Incident monitoring and response system

ABSTRACT

An incident monitoring and response system may include observer communication devices that are located in an area where an incident is occurring within a monitored region. A monitoring station sends an incident mode message to observer communication devices within the area. Upon receiving the incident mode message, the observer communication devices enter an incident mode in which the functionality of the device is limited. This limited functionality includes limiting the types of communications that an observer may engage in and the types of applications that can be accessed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/099,688, filed on Apr. 15, 2016, and entitled “INCIDENT MONITORINGAND RESPONSE SYSTEM”, which is incorporated herein by reference.

BACKGROUND

Public areas such as schools, airports, malls, and theaters haverecently been the target of large-scale criminal incidents. Suchincidents include physical attacks such as mass shootings and terroristincidents, but also include attacks on property and social order such asriots, flash mobs and violent protests. Incidents are often coordinatedthrough communication mediums such as cell phones, text messages, socialmedia, and chat rooms. Using such technologies, a group of activeshooters or a flash mob may coordinate their activities in a manner toinflict maximum damage or disruption while avoiding law enforcementpersonnel.

Individuals in the area of the incident may observe the incident orcircumstances related to an incident. For example, observers may seeassailants, hear gunshots, see or hear victims, and observe the progressof responders such as police and medical personnel. A typical observerwill have a communication device such as a smart phone, smart watch, ortablet device with them while observing the incident. Thesecommunication devices provide various communication tools such ascellular phone connectivity, text messages, messaging boards, and socialmedia outlets. They also may include sensors, cameras, microphones, andother tools that may be useful in acquiring information about anincident.

The proliferation of communication devices allows observers to provideinformation to incident reporting systems, law enforcement,acquaintances, or in some cases, anyone who is able to view a socialmedia feed. Observers often provide contradictory or irrelevantinformation regarding an incident, which makes it difficult for lawenforcement to discern the relevant facts to respond to the incident. Inaddition, the large volume and diversity of available informationincreases the difficulty of distinguishing relevant information fromfalse or irrelevant information. Many observers may begin to use a largeamount of bandwidth at the same time, increasing the load on thecommunication network in the area of the incident and possibly causingrelevant communications (e.g., from responders or direct observers) tobe blocked. Communications to third parties such as acquaintances orstrangers may cause more people to flock to the area of the incident inan effort to assist or out of curiosity. This response increases thenumber of bystanders in the area of the incident and may also causetraffic problems that prevent law enforcement or other responders fromreaching the incident.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other features of the present disclosure, its nature andvarious advantages will be more apparent upon consideration of thefollowing detailed description, taken in conjunction with theaccompanying drawings in which:

FIG. 1 shows an illustrative incident monitoring and response system inaccordance with some embodiments of the present disclosure;

FIG. 2 depicts a flow diagram depicting illustrative steps for operatingan incident monitoring and response system in accordance with someembodiments of the present disclosure;

FIG. 3 depicts an illustrative block diagram of an illustrative observercommunication device in accordance with some embodiments of the presentdisclosure;

FIG. 4 depicts an illustrative block diagram of an illustrativemonitoring station in accordance with some embodiments of the presentdisclosure;

FIG. 5 depicts an illustrative block diagram of an illustrativeresponder device in accordance with some embodiments of the presentdisclosure;

FIG. 6 depicts illustrative steps for operating an illustrative observercommunication device in accordance with some embodiments of the presentdisclosure;

FIG. 7 depicts illustrative steps for operating an illustrativemonitoring station in accordance with some embodiments of the presentdisclosure;

FIG. 8 depicts illustrative steps for operating an illustrativeresponder device in accordance with some embodiments of the presentdisclosure;

FIG. 9 depicts an exemplary monitored region in accordance with someembodiments of the present disclosure;

FIG. 10 depicts an exemplary sub-region of a monitored region inaccordance with some embodiments of the present disclosure;

FIG. 11 depicts an exemplary user interface of an observer communicationdevice in accordance with some embodiments of the present disclosure;

FIG. 12 depicts an exemplary responder user interface in accordance withsome embodiments of the present disclosure; and

FIG. 13 depicts an exemplary descriptive display of a responder userinterface in accordance with some embodiments of the present disclosure.

DETAILED DESCRIPTION

A method of controlling an observer communication device during anincident comprises receiving, via a first communication interface of aplurality of communication interfaces of the observer communicationdevice, one or more incident messages, wherein the one or more incidentmessages provide incident information and require the observercommunication device to enter an incident mode, controlling access ofone or more applications of the observer communication device to theplurality of communication interfaces based on the incident mode,generating an incident mode user interface for the observercommunication device based on the incident information, displaying theincident mode user interface at a display of the observer communicationdevice, controlling access of the one or more applications of theobserver communication device to the display based on the incident mode,receiving a user input associated with the incident mode at the userinterface, transmitting a response message to a monitoring system viaone or more of the plurality of communication interfaces, wherein theresponse message is based on the user input.

A communication device for operating in a normal mode and an incidentmode, the communication device comprises a plurality of communicationinterfaces, a user interface, a processing element, and one or memorydevices. During a normal mode the plurality of communication interfacesare accessible by a plurality of applications. During an incident modeone or more of the plurality of applications are unable to access theplurality of communications interfaces. During the normal mode theplurality of applications are able to provide information for display atthe user interface and to receive user inputs at the user interface.During the incident mode the plurality of applications are not able toprovide information for display at the user interface and to receiveuser inputs at the user interface. The processing element configured toexecute instructions, control the operation of the plurality ofcommunication devices, and control the operation of the user interface.The one or more memory devices store incident mode instructions. Theincident mode instructions cause the processing element to receive oneor more incident messages vie one or more of the plurality ofcommunication interfaces. The one or more incident messages provideincident information and require the observer communication device toenter an incident mode. The incident mode instructions further cause theprocessing element to initiate the incident mode at the plurality ofcommunications interfaces and the user interface, display an incidentmode user interface at a display of the user interface, receive a userinput associated with the incident mode from the user interface, andtransmit a response message to a monitoring system via one or more ofthe plurality of communication interfaces. The response message is basedon the user input.

A non-transitory computer-readable storage medium comprises instructionsstored therein, which when executed by one or more processors, cause theone or more processors to perform operations. Those operations comprisereceiving one or more incident messages from a first communicationinterface of a plurality of communication interfaces of an observercommunication device, wherein the one or more incident messages provideincident information and require the observer communication device toenter an incident mode, controlling access of one or more applicationsof the observer communication device to the plurality of communicationinterfaces based on the incident mode, generating an incident mode userinterface for the observer communication device based on the incidentinformation; providing information for the incident mode user interfaceto a display of the observer communication device, controlling access ofthe one or more applications of the observer communication device to thedisplay based on the incident mode, receiving a user input associatedwith the incident mode from the user interface, and providing a responsemessage to be transmitted to a monitoring system via one or more of theplurality of communication interfaces, wherein the response message isbased on the user input.

FIG. 1 depicts an exemplary incident monitoring and response system 1 inaccordance with some embodiments of the present disclosure. In oneembodiment, the incident monitoring and response system 1 may include amonitored region 10, a monitoring station 30, and responders 40.Communication devices within the monitored region 10 and communicationsdevices of responders 40 may communicate with monitoring station 30through a network 20 and communications links 12, 14, and 16.

A monitored region 10 may include any suitable region such as ajurisdictional area (e.g., a city, municipality, state, county, country,transportation district, etc.), a geographic region (e.g., a watershed,mountain range, valley, bay, river, etc.), a particular location (e.g.,a school, mall, sports venue, government building, factory, etc.), auser-defined region (e.g., a region defined by longitude and latitude,coordinates, regions defined by shapes or drawing tools, etc.), anyother suitable mechanism for defining a monitored region 10, or anycombination thereof. In an exemplary embodiment, a grid system such as aUniversal Transverse Mercator (UTM) system, Ordnance Survey system,Military Grid Reference System (MGRS), or any other suitable grid systemmay overlie the monitored region 10. The grid system may be used todefine locations of sub-regions within the monitored region 10 asdescribed herein.

In an embodiment, notifications may be provided to the monitoringstation 30, which may indicate that an incident may have occurred at alocation within monitored region 10. The notifications may be providedin a variety of manners, such as by an individual contacting 911, apolice or security service identifying an incident, monitoring of socialmedia activity, gunshot sensors, human or video monitoring ofsurveillance devices, any other suitable notification technique, or anysuitable combination thereof. The notifications may provide informationabout the incident such as the type of incident, description ofassailants, number of assailants, time of the incident, description ofinjured persons or property, any other suitable information, or anycombination thereof. As will be discussed herein, a monitoring station30 may identify a sub-region of the monitored region 10 that is impactedby the incident based on the notifications. The sub-region may beidentified in any suitable manner (e.g., jurisdictional regions,geographic regions, locations, ad-hoc regions, etc.), but in anexemplary embodiment is identified based on portions of the grid systemthat correspond to the where the incident is likely to be occurringwithin the monitored region 10. This is depicted in monitored region 10of FIG. 1 as the shaded portions of the grid.

The notifications from observers within a monitored region 10 may beprovided to monitoring station 30 over communication links 12 and 14 andnetwork 20. Moreover, in some embodiments, communications betweenmonitored region 10 and responders 40 may occur through communicationlinks 14 and 16 and network 20. The communication links 12, 14, and 16,and the network 20, may implement any suitable communication system orcombination thereof, such as cellular, Internet, satellite, radio,optical, and other suitable communication networks and methods.

Communications devices of observers within the sub-region of monitoredregion 10 may enter an incident monde in response to communications frommonitoring station 30. Any device that is connected to a communicationsystem (e.g., a cell phone, tablet, computer, radio, etc.) may receivethe notification to enter the incident mode, in which the functionalityof the communication device may be modified, for example, to limitavailable functionality, to provide incident reporting options, and toimplement monitoring. In this manner, the communication devices mayprovide information that is useful for incident response and monitoringwhile limiting detrimental communications. For example, excessive phonecalls, texts, and e-mails from a sub-region where an incident isoccurring may limit the ability of a monitoring station 30 or responders40 to address the most important communications or may attract unhelpfulonlookers, media, etc. Functionality such as social media may bemonitored by assailants or bystanders, complicating efforts to addressan incident. Other communications may be useful and may be enabled inresponse to an incident, such as reporting information about anassailant, number of assailants, presence of gunshots, location ofassailants, presence of injured persons, severity of injuries, and otherinformation that is directly relevant to responding to an incident.Components of the communication device may also be useful to providemonitoring for an incident. For example, a camera or microphone of amobile device may be used to receive video of an incident or analyzeaudio (e.g., gunshot detection).

Monitoring station 30 may perform the communication, analysis, control,and other functionality as described herein. The monitoring station 30can include a plurality of servers, computers, electronic devices, andhuman operators, and may be located at a central location or distributedover a number of facilities. In an exemplary embodiment, monitoringstation 30 may process notifications received from responders 40 andobservers within a monitored region 10, identify an impacted sub-regionwithin the monitored region 10 based on those notification, initiate anincident mode for observer communication devices within the sub-region,analyze data received from communication devices operating in incidentmode within the sub-region, and communicate with responders 40 regardingthe incident.

As described herein, monitoring station 30 may receive notificationsfrom a variety of sources such as phone calls, text messages, e-mails,social media, gunshot sensors, police reporting, and surveillanceequipment. The notifications may be analyzed automatically (e.g., byservers and computing devices), by human users working at the monitoringstation 30, or by a combination thereof. For example, in an embodiment,certain notifications such as social media feeds, text messages, sensordata and phone calls may be analyzed by an automated system initially,with summary information provided to a human operator. Notificationsthat are considered most relevant (e.g., notifications from police orother trusted individuals) may be prioritized for the human operator.Through the combination of electronic analysis and human analysis, alarge volume of notifications within a monitored region 10 may beprocessed.

Monitoring station 30 may also identify sub-regions of the monitoredregion 10 based on received notifications. Once the sub-region has beenidentified, information about observer communication devices within themonitored region 10 may be used to determine which observercommunication devices are within the sub-region. In an embodiment,information such as location data may be acquired based on cell towers,IP addresses, Wi-Fi addresses, GPS data, any other suitable locationinformation, or any combination thereof. In some embodiments,communication devices running an incident monitoring application may bepolled by the monitoring station 30 to provide location information(e.g., GPS data). Once the observer communication devices within thesub-region have been identified by monitoring station 30, monitoringstation 30 may provide the incident mode message to the communicationdevices (e.g., through network 20 and communication links 12 and 14). Asdescribed herein, the observer communication devices within thesub-region may then enter the incident mode, invoking a limitedfunctionality with specialized user interfaces and monitoringinterfaces.

Monitoring station 30 may receive monitored data from observercommunication devices within a sub-region of monitored region 10 andfrom responders 40. Based on this received data, monitoring station 30may determine information such as number of assailants, assailantdescriptions, type of incident, quantity of injuries, location ofassailants, severity of injuries, presence of responders, demographicinformation about individuals within the sub-region, any other suitableinformation, or any combination thereof. Monitoring station 30 may alsoreceive surveillance signals such as signals from communication devicesoperating in incident mode (e.g., camera and microphone signals), othersurveillance equipment within the sub-region, and surveillance providedby responders 40. Based on this information, the monitoring station 30may control the information that is available within the incident mode,as well as provide information to responders to allow them to betterrespond to the incident.

Monitoring station 30 may provide information for responders 40.Responders 40 may have radios, displays, augmented reality devices, andother equipment that provides them with access to information that maybe used to respond to incidents. Based on the information that isprovided from the notifications, from communication devices in theincident mode, and from responders 40 themselves, the monitoring station30 may tailor information to assist the responders in responding to theincident, and in some embodiments, the information may also be tailoredbased on the type of responder (e.g., medical personnel, policepersonal, SWAT teams, military personal, etc.). Information may includeexpected locations of assailants, identifying information forassailants, expected locations of observers within the sub-region,injuries, severity of injuries, locations of other responders (e.g., byresponder type), any other suitable information to assist in respondingto the incident, or any combination thereof.

Responders 40 may have a variety of equipment and electronic devicesthat assist them in responding to incidents, such as radios, displays,smart watches, smart phones, tablets, computers, augmented realitydevices, and other suitable general or customized devices. These devicesmay allow the responders 40 to display information about an incident,and to also provide monitoring data to the monitoring station 30 (e.g.,through network 20 and communication links 14 and 16), for example,through customized interfaces of an application, as monitoring data frombody cameras or other electronic devices, through speech information, orin any other suitable manner. In this manner, responders 40 may bothreceive information for responding to an incident and provideinformation to assist in monitoring of the incident.

FIG. 2 depicts exemplary steps for operating an incident monitoring andresponse system 1 in accordance with some embodiments of the presentdisclosure. The steps of FIG. 2 are provided in an exemplary sequenceand flow, and it will be understood that some steps may be inserted orremoved, and that a different flow and steps may be implemented.

In step 202, monitoring station 30 may receive notifications from withina monitored region 10 (e.g., from observers, surveillance devices, andanalysis of electronic communications) and from responders 40. Based onthese notifications, a monitoring station 30 may determine informationabout an event, such as a sub-region of the monitored region 10 in whichthe incident is occurring. Other information, such as information aboutthe type of incident, may also be determined based on the notifications.Processing may then continue to step 204.

At step 204, the monitoring station 30 may determine, based on thereceived notifications, where the sub-region related to the incident islocated within the monitored region 10. Although the sub-region may beidentified in any suitable manner, in embodiments an expected incidentlocation may be identified and the sub-region may include a buffer areaaround the incident location. In an embodiment, the size of the bufferarea may be based on a confidence level for the incident location (e.g.,with a larger buffer area corresponding to a lower confidence level).Once the sub-region is identified, monitoring station 30 may determinewhich observer communication devices are located within the sub-region.Once the observer communication devices are identified, incident modenotifications may be provided to the observer communication devices. Insome embodiments, the incident mode notification may be tailored basedon information about the incident, the type of communication device,expected proximity to the incident, information about the observer, orin any other suitable manner. The incident mode notification then may betransmitted to the observer communication devices within the sub-regionof the monitored region 10. Processing may then continue to step 206.

At step 206, each observer communication device receiving the incidentmode notification may enter the incident mode. In some embodiments, theincident mode notification may include parameters that may restrict thetypes of activities that are available in the incident mode, the typesof user inputs that are allowed in the incident mode, and the type ofmonitoring that is provided by the communication devices in the incidentmode. Based on this information, each communication device may enter itsincident mode, disabling certain functionality (e.g., certainapplications and communication functionality), providing specific inputsfor use in providing information about the incident, and monitoring toprovide surveillance information of the incident. Processing may thencontinue to step 208.

At step 208, each observer communication device within the sub-region ofthe monitored region 10 may collect data about the incident. Asdescribed herein, an observer may be provided with a limited menu ofinputs that allow the user to provide specific information that is mostrelevant to an incident. Also as described herein, a communicationdevice may provide monitoring such as through a camera or microphone ofthe communication device. This collected data may then be provided fromthe communication devices within a sub-region of the monitored region 10to the monitoring station 30. Processing may then continue to step 210.

At step 210, monitoring station 30 may provide notifications toresponders 40. As described herein, the notifications may provideinformation related to the incident and may be tailored based on thetype of responder 40. Responders 40 may also collect information that isprovided to the monitoring station 30, as described herein. Processingmay then continue to step 212.

At step 212, processing station 30 may process the information and datareceived from the communication devices within the sub-region of themonitored region 10 and from responders 40. This information may becompiled and analyzed for use in determining information about theincident. Processing may then continue to step 214.

At step 214, processing system 30 may determine whether the incident isover, based on the received and processed information. For example, insome embodiments, certain types of responders may be able to provide aninput to an electronic device or other notification indicating that anincident is over. If the incident is over, users of communicationdevices within the sub-region and responders 40 may be provided withnotification, communication devices within the sub-region may exit theincident mode, and the incident may end. If the incident has not ended,processing may continue to step 216.

At step 216, the processing system may generate updates based on thereceived and processed data and information. As described herein, theprocessing station 30 may generate various types of updates, such asmodifying the sub-regions that are impacted by the incident (e.g.,allowing some communication devices to exit the incident mode, providingnotifications that the incident mode is being exited, and causing othercommunication devices to enter into the incident mode), may updateoptions that are available to communication devices within thesub-region in the incident mode, and may provide information toresponders about the incident and locations of other responders. Oncethe updates have been generated, processing may continue to step 218.

At step 218, the incident updates may be transmitted to thecommunication devices within the sub-region and to the responders 40.The communication devices and responders 40 may update the informationprovided to users and the operation of monitoring equipment based on theupdates, and processing may return to step 208 to collect additionaldata from the communication devices within the sub-region and fromresponders 40.

FIG. 3 depicts a block diagram of an exemplary observer communicationdevice 300 in accordance with some embodiments of the presentdisclosure. Although particular components are depicted in a particulararrangement in FIG. 3, it will be understood that observer communicationdevice 300 may include additional or fewer components, that componentsthereof may be rearranged in any suitable manner, and one or morecomponents may be implemented on one or more other devices. Although anobserver communication device may be any suitable device that is capableof communicating using any suitable communication interface, in anexemplary embodiment the observer communication device 300 may be anelectronic device running an operating system and applications, such asa smart watch, smart phone, phablet, tablet, augmented reality lenses,laptop, or desktop. In an embodiment, the observer communication devicemay include a processing element 302, memory 304, a user interface 306,sensors 308, and communications interfaces 310.

Processing element 302 may include any suitable processors, hardware,memory, or other components that perform the processing functionalitydescribed herein. The processing element 302 may execute softwareinstructions in machine readable form on a tangible non-transitorycomputer readable storage medium, which may be accessed from anysuitable memory (e.g., memory 304). In some embodiments, certainfunctionality of processing element may be implemented as hardware logic(e.g., software-designed hardware such as hardware description language(HDL) hardware that implements functionality described by the HDLsoftware), computer readable instructions running on a processor, or anysuitable combination thereof.

Memory 304 may include any suitable tangible or non-transitory storagemedium that stores information, but does not include transient orpropagated signals. Memory 304 may be any suitable memory device orcombination thereof, such as flash memory, disks, ROM, EPROM, EEPROM,RAM, SRAM, optical or magnetic storage devices, or any othernon-transitory medium that stores information that is accessed by aprocessor or computing device. In an embodiment, memory 304 may includea plurality of sets of instructions, including system instructions 324,application communication instructions 320, application user interfaceinstructions 322, and application monitoring instructions 326. Asdescribed herein, in an embodiment system instructions 324 may includegeneral instructions for the observer communication device 300 such asan operating system, application program interfaces (APIs) forinteracting with applications and programs, and instructions forcontrolling the various components of the observer communication device300 (e.g., APIs allowing applications to control user interface 306,sensors 308, and communications interfaces 310). The functionality ofthe incident mode may be implemented through an application program,which may include a plurality of software components such as applicationcommunication instructions 320, application user interface instructions322, and application monitoring instructions 326. Although theinstructions of the incident mode application are described herein asimplementing different functionality with different instructions, itwill be understood that the instructions of the incident modeapplication may be implemented as an integrated application or separateportions or subroutines.

User interface 306 may include user interface components such as atouchscreen, display, keyboard, mouse, voice recognition, buttons,biometric readers, gesture recognition, augmented reality display, anyother suitable user interface components, or any combination thereof. Inan embodiment, the user interface 306 may include at least some form ofdisplay (e.g., a screen of a smart watch or smart phone, or a display ofan augmented reality device) that may provide specific information to anobserver while in the incident mode, as well as some form of user input(e.g., a touchscreen of a smart watch or smart phone, or gesturerecognition of an augmented reality device) to allow the user to provideresponses and other information that may be transmitted to monitoringstation 30.

Sensors 308 may include various types of components and devices such asvideo cameras, microphones, biometric sensors, time-of-flight sensors,accelerometers, gyroscopes, environmental sensors (e.g., temperature,barometric pressure, humidity, etc.), physiological sensors (e.g., heartrate, blood pressure, pulse, etc.), any other suitable sensors, or anycombination thereof. In an embodiment, the sensors 308 may includesensors that allow for the observer communication device 300 to provideremote monitoring of the incident, such as video cameras and audiosensors of smart phone or augmented reality device.

Communications interfaces 310 may include wireless and wired interfacesfor communicating locally and over a network such as a cellularcommunications network or the internet. Exemplary wireless interfacesmay include WiFi, cellular, Bluetooth, near field communications (NFC),infrared, radio, satellite, any other suitable wireless communicationinterface, or any combination thereof. Exemplary wired communicationinterfaces may include Ethernet, USB, Firewire, telephone lines, DSL,cable connections, fiber optics, any other suitable wired communicationinterface, or any combination thereof. In an embodiment, an observercommunication device may include cellular, WiFi, Bluetooth and USBcommunications interfaces 310.

In some embodiments, application communication instructions 320 mayinclude instructions for the incident mode application to receivecommunications indicating that the incident mode should be initiated andto restrict and control the operations of communication interfaces 310and other applications running on the observer communication device 300in response to the incident mode. Incident mode messages may be receivedat one or more of communications interfaces 310, and the processingelement 302 may determine the response to the incident mode messagesbased on the application communication instructions 320. In anembodiment, that response may include shutting down a subset ofcommunication interfaces 310 or prohibiting the communication ofinformation from some or all applications other than the incident modeapplication. In some embodiments, the application communicationinstructions 320 may cause processing element 302 to stop the executionof some or all other applications, preventing those applications fromcommunicating over communication interfaces 310, from consuming batterypower, or from using processing and memory resources. In an embodiment,application communication instructions 320 may also include instructionsfor transmitting user inputs and monitored information to a monitoringstation 30, through communications interfaces 310.

In some embodiments, application user interface (UI) instructions 322may include instructions for controlling the user interfaces 306 inresponse to the incident mode. The options that are presented to anobserver may be modified based on the initiation of the incident modeand the type of incident. In an embodiment, application UI instructions322 may cause a user interface 306 component (e.g., a display) toprovide information indicating that the incident is occurring,information about the incident (e.g., a description of assailants),instructions relating to the incident (e.g., to stay or remain at alocation), options for providing information about an incident (e.g.,description of assailants, information about observers in the area,information relating to gunshots and injuries), and other availablefunctionality (e.g., a limited interface for contacting emergencypersonnel). In an embodiment, the user interface for the incident modemay be the only user interface that is available to the operator, suchthat the operator is not permitted to access other programs orapplications of the operator communications device 300. Application UIinstructions 322 may include instructions for processing inputs receivedfrom user interfaces 306, in order to determine whether informationshould be provided to a monitoring station 30 and in order to preparethe information to be provided to monitoring station 30.

In some embodiments, application monitoring instructions 326 may includeinstructions for operating one or more of sensors 308 in order toprovide monitoring about an incident. In response to the initiation ofthe incident mode, the application monitoring instructions 326 may causethe override of other functionality of one or more sensors that areuseful for providing monitoring of incident. In an embodiment, thesesensors (e.g., cameras, microphones, and GPS) may be employed to monitorfor information about an incident. In some embodiments, applicationmonitoring instructions 326 may include instructions for performingpre-processing of data received from some or all of the sensors (e.g.,identifying a gunshot from a microphone signal and creating gunshotnotification message including a timestamp and GPS location, orperforming image analysis to identify persons of interest from a videofeed). The raw feeds and/or pre-processed data may be provided tomonitoring station 30.

FIG. 4 depicts a block diagram of an exemplary monitoring system 400 ofa monitoring station in accordance with some embodiments of the presentdisclosure. Although particular components are depicted in a particulararrangement in FIG. 4, it will be understood that monitoring system 400may include additional or fewer components, that components thereof maybe rearranged in any suitable manner, and one or more components may beimplemented on one or more other devices. Although a monitoring system400 may be any suitable system that is capable of monitoring andresponding to incidents, in an exemplary embodiment the monitoringsystem 40 may be a computer operating at a monitoring station 30, whichmay be in communication with other computing devices such as servers toimplement the functionality described herein. Although the functionalityof the monitoring system 400 may be described herein as being executedby a single computing device, it will be understood that any suitablefunctionality of the monitoring system 40 may be distributed over aplurality of devices, and in some embodiments, distributed over aplurality of monitoring stations. In an embodiment, the monitoringsystem 400 may include a processing element 402, memory 404, operatorinterface 406, observer communication interfaces 408, and respondercommunication interfaces 410.

Processing element 402 may include any suitable processors, hardware,memory, or other components that perform the processing functionalitydescribed herein. The processing element 402 may execute softwareinstructions in machine readable form on a tangible non-transitorycomputer readable storage medium, which may be accessed from anysuitable memory (e.g., memory 404). In some embodiments, certainfunctionality of processing element may be implemented as hardware logic(e.g., software-designed hardware such as hardware description language(HDL) hardware that implements functionality described by the HDLsoftware), computer readable instructions running on a processor, or anysuitable combination thereof.

Memory 404 may include any suitable tangible or non-transitory storagemedium that stores information, but does not include transient orpropagated signals. Memory 404 may be any suitable memory device orcombination thereof, such as flash memory, disks, ROM, EPROM, EEPROM,RAM, SRAM, optical or magnetic storage devices, or any othernon-transitory medium that stores information that is accessed by aprocessor or computing device. In an embodiment, memory 404 may includea plurality of sets of instructions, including system instructions 424,monitoring instructions 420, observer instructions 422, and responderinstructions 326. As described herein, in an embodiment systeminstructions 424 may include general instructions for the monitoringsystem 400 such as an operating system, application program interfaces(APIs) for interacting with applications and programs, and instructionsfor controlling the various components of the monitoring system 300(e.g., APIs allowing applications to operator interface 406, observercommunication interfaces 408, and responder communication interfaces410). In an embodiment, the monitoring system may be a specializedcomputing system for processing reports of incidents, processinginformation relating to incidents, determining information to beprovided to an operator of the monitoring system 400, and determininginformation to be provided to an observers and responders.

Operator interface 406 may include user interface components such as atouchscreen, display, keyboard, mouse, voice recognition, buttons,biometric readers, gesture recognition, augmented reality display, anyother suitable user interface components, or any combination thereof,that allow an operator of the monitoring system 400 to interact with themonitoring system 400. In an embodiment, the operator interface 406 mayinclude a computing device having a touchscreen display, keyboard,mouse, and voice recognition, such that the operator can interact withthe monitoring system in a variety of ways. In this manner, themonitoring system can process information and provide raw information,analyses, and statistics to an operator, such that an operator cancontrol a response to incident. In some embodiments, the monitoringsystem may provide preliminary analyses of an incident, such as apredicted area for a sub-region or descriptive information relating tothe incident. The operator may then modify or adjust the preliminaryanalysis, for example, by modifying a map display to adjust a sub-regionfor the incident.

Observer communications interfaces 408 may include wireless and wiredinterfaces for communicating with observers over a network such as acellular communications network or the internet. Exemplary wirelessinterfaces may include WiFi, cellular, radio, satellite, any othersuitable wireless communications interface, or any combination thereof.Exemplary wired communications interfaces may include Ethernet,telephone lines, DSL, cable connections, fiber optics, any othersuitable wired communications interface, or any combination thereof. Inan exemplary embodiment, observer communications interfaces 408 mayprovide a high-speed direct connection to communications networks suchas cellular networks and the internet to facilitate a high volume ofcommunications with observers.

Responder communications interfaces 410 may include wireless and wiredinterfaces for communicating with responders over a network such as acellular communications network, the internet, or a dedicatedcommunication channel. Exemplary wireless interfaces may include WiFi,cellular, radio, satellite, any other suitable wireless communicationsinterface, or any combination thereof. Exemplary wired communicationsinterfaces may include Ethernet, telephone lines, DSL, cableconnections, fiber optics, any other suitable wired communicationsinterface, or any combination thereof. In an exemplary embodiment,responder communications interfaces 408 may provide a dedicatedcommunication channel to responders, for example, via cellular networksand satellite/radio communications. In some embodiments, one or more ofobserver communications interfaces 408 and responder communicationsinterfaces 410 may be shared for both observer and respondercommunications (e.g., a cellular or internet connection).

In some embodiments, monitoring instructions 420 may includeinstructions for the monitoring system 400 to perform operationsincluding processing incoming notifications and monitoring information,interacting with an operator through the operator interface 406,identifying a sub-region, and determining information about an incident(e.g., information about assailants, observers, injuries, etc.). Asdescribed herein, notifications regarding an incident may be receivedvia observer communications interfaces 408 and responder communicationsinterfaces 410, and may include information such as phone calls, textmessages, e-mails, social media feeds, gunshot sensors, and surveillanceequipment. In some embodiments, aspects of this information may beautomatically analyzed based on processing element 402 executingmonitoring instructions to extract information such as location of anincident from the received notifications. In this manner, the monitoringsystem may provide an automated analysis of the location of a sub-regionwhere an incident is occurring, and in some embodiments, may provide apreliminary analysis that may be modified by an operator via operatorinterface 406. The monitoring instructions 420 may also includeinstructions for determining information about an incident such asinformation about assailants and injuries to observers based on receiveddata. In some embodiments, the monitoring instructions 420 mayfacilitate the automated analysis of the incoming information (e.g.,based on known inputs from a incident mode application running onobserver communication devices 300, based on automated analysis of videoand audio feeds, etc.). In some embodiments, information or analysis maybe provided to the operator via operator interface 406 for furtheranalysis.

In some embodiments, observer communications instructions 422 mayinclude instructions for communicating with observer communicationdevices 300 via observer communications interfaces 408 and fordetermining the content of incident mode messages to be transmitted tothe observer communications devices. As described herein, observercommunication devices 300 may provide information such as notifications,observer responses to the incident mode application, and monitoringinformation from the incident mode application. The monitoring system400 may provide information within incident mode messages. The observercommunications instructions 422 may determine the content of thesecommunications and the communications medium for exchanging thesecommunications. For example, the observer communications instructionsmay access information about the incident (e.g., as determined bymonitoring instructions 420) and generate incident messages for observercommunications devices 300. In an embodiment, the incident messages maybe differentiated based on characteristics such as the type ofcommunication device, the proximity of the observer to the incident, andthe identity of the observer. In some embodiments, the observercommunications instructions may also determine whether informationshould be transmitted over a particular communications medium (e.g., ifcellular communications channels are busy, certain communications mayonly be exchanged vie an internet connection).

In some embodiments, responder communications instructions 426 mayinclude instructions for communicating with responder devices 500 viaresponder communications interfaces 410 and for determining the contentof incident mode messages to be transmitted to the respondercommunications devices 500. As described herein, responder devices 500may provide information such as responder notifications, responder datawhile responding to an incident, monitoring feeds from responders, andother information relevant to the incident. The monitoring system 400may provide information to the responder devices 500 such as informationabout assailants, observers, gunshots, injuries, and other responders.In some embodiments, information for generating a descriptive displaymay be provided by monitoring system 400. In some embodiments, thisinformation may include an overlay of information relating toassailants, observers, gunshots, injuries, and other responders over amap region. The responder communications instructions 422 may performinitial processing on incoming information from responders and may alsodetermine this information that is transmitted to responders. In anembodiment, messages may be differentiated based on characteristics suchas the type of communication device, the proximity of the responder tothe incident, and the type of responder. In some embodiments, theresponder communications instructions 426 may also determine whetherinformation should be transmitted over a particular communicationsmedium (e.g., if cellular communications channels are busy, certaincommunications may only be exchanged via an internet connection, ordedicated communications paths such as through a mobile communicationsystem (e.g., communications drones, vans, etc.)).

FIG. 5 depicts a block diagram of an exemplary responder device 500 inaccordance with some embodiments of the present disclosure. Althoughparticular components are depicted in a particular arrangement in FIG.5, it will be understood that responder device 500 may includeadditional or fewer components, that components thereof may berearranged in any suitable manner, and one or more components may beimplemented on one or more other devices. Although a responder devicemay be any suitable device that is utilize by a responder such as lawenforcement, medical personnel, fire fighters, SWAT, or military, in anexemplary embodiment the responder device 500 may be an electronicdevice running an operating system and applications, such as a smartwatch, smart phone, phablet, tablet, augmented reality lenses, laptop,or desktop. In an embodiment, the responder device may include aprocessing element 502, memory 504, a user interface 506, sensors 508,and communications interfaces 510.

Processing element 502 may include any suitable processors, hardware,memory, or other components that perform the processing functionalitydescribed herein. The processing element 502 may execute softwareinstructions in machine readable form on a tangible non-transitorycomputer readable storage medium, which may be accessed from anysuitable memory (e.g., memory 504). In some embodiments, certainfunctionality of processing element may be implemented as hardware logic(e.g., software-designed hardware such as hardware description language(HDL) hardware that implements functionality described by the HDLsoftware), computer readable instructions running on a processor, or anysuitable combination thereof.

Memory 504 may include any suitable tangible or non-transitory storagemedium that stores information, but does not include transient orpropagated signals. Memory 504 may be any suitable memory device orcombination thereof, such as flash memory, disks, ROM, EPROM, EEPROM,RAM, SRAM, optical or magnetic storage devices, or any othernon-transitory medium that stores information that is accessed by aprocessor or computing device. In an embodiment, memory 504 may includea plurality of sets of instructions, including system instructions 524,responder communication instructions 520, responder user interfaceinstructions 522, and responder monitoring instructions 526. Asdescribed herein, in an embodiment system instructions 524 may includegeneral instructions for the responder device 500 such as an operatingsystem, application program interfaces (APIs) for interacting withapplications and programs, and instructions for controlling the variouscomponents of the responder device 500 (e.g., APIs allowing applicationsto control user interface 506, sensors 508, and communicationsinterfaces 510). The functionality of the responder device may beimplemented through an application program, which may include aplurality of software components such as application communicationinstructions 520, application user interface instructions 522, andapplication monitoring instructions 526. Although the instructions ofthe incident mode application are described herein as implementingdifferent functionality with different instructions, it will beunderstood that the instructions of the incident mode application may beimplemented as an integrated application or separate portions orsubroutines.

User interface 506 may include user interface components such as atouchscreen, display, keyboard, mouse, voice recognition, buttons,biometric readers, gesture recognition, augmented reality display, anyother suitable user interface components, or any combination thereof. Inan embodiment, the user interface 506 may include at least some form ofdisplay (e.g., a screen of a smart watch or smart phone, or a display ofan augmented reality device) that may provide specific information to aresponder while in the incident mode, as well as some form of user input(e.g., a touchscreen of a smart watch or smart phone, or gesturerecognition of an augmented reality device) to allow the user to controldisplay and menus of the responder device, control communications withother responders, and communicate with the monitoring station 50. Insome embodiments, user interface 506 may also facilitate communicationswith other responder equipment (e.g., law enforcement or medicalequipment) to control aspects of operations of that equipment.

Sensors 508 may include various types of components and devices such asvideo cameras, microphones, biometric sensors, time-of-flight sensors,accelerometers, gyroscopes, environmental sensors (e.g., temperature,barometric pressure, humidity, etc.), physiological sensors (e.g., heartrate, blood pressure, pulse, etc.), infrared sensors, any other suitablesensors, or any combination thereof. In an embodiment, the sensors 508may allow for the responder device 500 to access information that may beused to directly update a display of the responder device 500, toprovide remote monitoring of the incident for the monitoring station 30,to provide information to other responder equipment, and to control theoperations of other responder equipment.

Communications interfaces 510 may include wireless and wired interfacesfor communicating locally and over a network such as a cellularcommunications network or the internet. Exemplary wireless interfacesmay include WiFi, cellular, Bluetooth, near field communications (NFC),infrared, radio, satellite, any other suitable wireless communicationinterface, or any combination thereof. In some embodiments, short- andmedium-range wireless interfaces may facilitate communications betweenresponders, while cellular and other long-range interfaces may be usedfor communications with a monitoring station 30. In some embodiments,the responder device may also include wired interfaces that mayperiodically connect to a wired interface such as Ethernet, USB,Firewire, telephone lines, DSL, cable connections, fiber optics, anyother suitable wired communication interface, or any combinationthereof.

In some embodiments, responder communication instructions 520 mayinclude instructions for the responder device 500 to communicate withthe monitoring station 30 via communications interfaces 510, tocommunicate with other responder devices 500 via communicationsinterfaces 510, and to process information that is sent and receivedduring these communications. The responder communication instructions520 may process incoming data from the monitoring station 30 or otherresponder devices 500, analyze the data, and prepare the data for use byresponder device 500. The responder communication instructions may alsoanalyze and format data for transmission to the monitoring station 30and other responder devices 500. In some embodiments, such analysis andformatting may include a preliminary determination of whether certaindata should be transmitted to a monitoring station or another responderdevice 500 (e.g., a preliminary analysis of an audio signal thatdetermines that gunshots may have been heard in the area, or acomparison of environmental or physiological information to athreshold). In some embodiments, responder communication instructionsmay also include instructions for determining the appropriatecommunications interface for handling certain types of communications,for example, based on channel traffic and interference.

In some embodiments, responder user interface (UI) instructions 522 mayinclude instructions for controlling the user interfaces 506 of theresponder device 500. The options that are presented to a responder maybe modified based on the information received from the monitoringstation 30 and other responder devices 50. In an embodiment, responderUI instructions 522 may cause a user interface 506 component (e.g., adisplay) to provide information indicating that the incident isoccurring, information about the incident (e.g., a description ofassailants, observers, gunshots, injuries, and other responders), adescriptive display for the incident (e.g., a visual display depictinginformation about the incident over a map of the sub-region), optionsfor providing information about an incident (e.g., description ofassailants, information about other responders in the area, informationrelating to gunshots and injuries), and other available functionality(e.g., communication interfaces for contacting other responders,responder equipment that may be controlled through the user interface,physiological measurements for the responder, etc.). Responder UIinstructions 522 may include instructions for processing inputs receivedfrom user interfaces 506, in order to determine whether informationshould be provided to a monitoring station 30 and other responderdevices 500, and in order to prepare the information to be provided tomonitoring station 30 and other responder devices 500.

In some embodiments, responder monitoring instructions 526 may includeinstructions for operating one or more of sensors 508 in order toprovide monitoring about an incident. In response to the communicationsfrom the monitoring station 30 or an input at user interface 506, theresponder monitoring instructions 526 may cause one or more sensors toacquire data that is useful for providing monitoring of incident. In anembodiment, these sensors (e.g., cameras, microphones, and GPS) may beemployed to monitor for information about an incident. In someembodiments, responder monitoring instructions 526 may includeinstructions for performing pre-processing of data received from some orall of the sensors (e.g., identifying a gunshot from a microphone signaland creating gunshot notification message including a timestamp and GPSlocation, or performing image analysis to identify persons of interestfrom a video feed). The raw feeds and/or pre-processed data may beprovided to monitoring station 30.

FIG. 6 depicts exemplary steps for a monitoring station 30 of anincident monitoring and response system 1 to identify incidents andcommunicate with observers and responders in accordance with someembodiments of the present disclosure. The steps of FIG. 6 are providedin an exemplary sequence and flow, and it will be understood that somesteps may be inserted or removed, and that a different flow and stepsmay be implemented.

At step 602, a monitoring station 400 may receive notifications throughcommunications interfaces such as observer communications interfaces 408and responder communications interfaces 410. As described herein,notifications include information such as electronic communications(e.g., e-mail and text messages), phone calls, inputs of the specializedapplications, feeds from surveillance equipment, communications fromgunshot sensor, and notifications from any other suitable equipment thatis useful for determining whether an incident is occurring within anarea. Processing element 402 may execute instructions (e.g., monitoringinstructions 420) to process these notifications. In some embodiments,information from the notifications may be compiled into a common dataformat that may be analyzed by a computing system (e.g., processingelement 402 executing monitoring instructions 420 and one or more othercomputers of the monitoring station 30 or incident monitoring andresponse system 1) and by an operator (e.g., based on processing element402 executing monitoring instructions 420 and interfacing with a displayand user interface of operator interface 406). Once the notificationshave been received and processed, processing may continue to step 604.

At step 604, processing element 402 may execute instructions (e.g.,monitoring instructions 420) to identify a sub-region of the monitoredregion 10 in which an incident is occurring. The sub-region may beidentified by monitoring station 400, other computing systems of themonitoring station 30 or incident monitoring and response system 1, byan operator of the monitoring system 400, or any combination thereof. Inan exemplary embodiment, the sub-region may be associated with a portionof a grid system overlaying the monitored region 10. Once a sub-regionhas been identified, processing may continue to step 606.

At step 606, processing element 402 may execute instructions (e.g.,monitoring instructions 420) to determine information about theincident. As described herein, notifications may be provided from anumber of different sources and types of sources. This information maybe compiled to be analyzed by monitoring system 400, other computingsystems of monitoring station 30 or incident monitoring and responsesystem 1, one or more operators at monitoring station 30, or anycombination thereof. Based on this wide variety of information,information about the incident may be determined, such as locations ofassailants, locations of bystanders, locations of responders, number ofassailants, assailant descriptions, presence of gunshots, injuries,severity of injuries, locations of available responders, any othersuitable information, or any combination thereof. Once this informationis determined, processing may continue to step 608.

At step 608, processing element 402 may execute observer instructions422 to provide incident mode messages to observers via observercommunications interfaces 408. In some embodiments, different incidentmode messages may be tailored to different observers based on factorssuch as location within a sub-region, demographic information about theobserver, available resources within a communication device (e.g., formonitoring), and other relevant information relating to the observer andtheir relation to the incident. Incident mode messages may includeinstructions to disable or modify the functionality of certainapplications and communication resources, to generate a custom userinterface and audio for reporting information about the incident, and toestablish monitoring feeds using resources of communications devices.Once the incident mode messages have been transmitted to the observerswithin the sub-region of the monitored region 10, processing maycontinue to step 610.

At step 610, processing element 402 may execute responder instructions426 to generate and send incident mode messages to responders. Incidentmode messages may be tailored to responders based on information such asthe type of responder (e.g., police officer, SWAT team, military,medical, emergency medical) and information about the incident (e.g.,proximity to the incident, type of incident, severity of incident,number of injuries at the incident, types of injuries at the incident).The incident mode messages may provide information for an enhanceddisplay and user inputs to be provided to responders, for example, adisplay showing locations of assailants, locations of observers,injuries, types of injuries, locations of responders, descriptiveinformation for assailants and observers, and other information relatingto the incident. In some embodiments, this information may be providedin an interactive visual descriptive display that overlays a map of thesub-region. The provided user interface may also allow for entry ofspecialized information relating to the incident as described herein.Once the incident mode messages have been sent to responders in thesub-region or in a suitable area relative to the sub-region, processingmay continue to step 612.

At step 612, monitoring system 400 may receive data from observers viaobserver communications interfaces 408, and processing element 402 mayexecute instructions of observer instructions 422 to process thereceived data. In an embodiment, the received data may include inputsprovided by observers using the specialized user interface, as well asmonitored information from the communication devices of the observers(e.g., video feeds, audio feeds, and analysis of video and audio feeds,such as identification of gunshots). The received data may be processedand formatted for analysis, and processing may continue to step 614.

At step 614, incident data may be received from responders via respondercommunications interfaces 410, and may be processed by processingelement 402 executing instructions of responder instructions 426.Received data from responders may include inputs to a specializedinterface, data such as GPS data, visual and audio feeds from monitoringequipment, and automated reporting from responder devices (e.g., weaponsand medical equipment). The received data may be processed and formattedfor analysis, and processing may continue to step 616.

At step 616, processing element 402 of monitoring system 400 may executemonitoring instructions 420 to process the received incident data.Information about the received incident data may be analyzed in anautomated manner, by one or more operators (e.g., using operatorinterface 406), or by a combination thereof. Based on this processing,the sub-region of the monitored region 10 may be updated, parameters forthe incident mode for operators may be updated, and parameters for theincident mode for the responders may be updated. In addition, it mayalso be determined that an incident is over, such that instructions maybe provided to observers and responders, and observer communicationdevices may be instructed to exit the incident mode. Once the incidentdata has been processed, processing may continue to step 618.

At step 618, processing element 402 of monitoring system 400 may executemonitoring instructions 420 and to determine whether an aspect of theincident should be updated, as determined by the processing of step 616.If incident information should not be updated, processing may return tostep 612, allowing monitoring system 400 to receive additional incidentdata from observers and responders, and to continue to process the data.If the incident information should be updated, processing may continueto step 620.

At step 620, processing element 402 of monitoring system 400 may executemonitoring instructions 420 to determine whether an incident is over. Ifthe incident is not over, and new incident mode information is to beprovided to the operator and/or the responders, processing may return tostep 604. If the incident is over, processing may continue to step 622.

At step 622, processing element 402 of monitoring system 400 may executeobserver instructions 422 to communicate messages indicating that theincident is over to observers via observer communications interfaces408. The messages may include information relating to the incident andinstructions for leaving the sub-region. In some embodiments, theinformation may also include further user input/output options togetherwith follow-up information about the incident. Once the messages havebeen sent to the observers, processing may continue to step 624.

At step 624, processing element 402 of monitoring system 400 may executeresponder instructions 426 to communicate a messages indicating that theincident is over to responders over responder communications interfaces410. The message may include information such as information describingthe incident, information relating to further responder response to theincident, information relating to instructions as to how to exit thesub-region, any other suitable information, or any combination thereof.In some embodiments, the message may also include additionalinput/output for the responders to provide additional information aboutthe incident. Once the messages have been sent to the responders, theprocessing may end.

FIG. 7 depicts exemplary steps for operating a observer communicationdevice in an incident mode in accordance with some embodiments of thepresent disclosure. The steps of FIG. 7 are provided in an exemplarysequence and flow, and it will be understood that some steps may beinserted or removed, and that a different flow and steps may beimplemented.

At step 702, processing element 302 of observer communication device 300may execute instructions of application instructions 320 to receive anincident mode notification via communications interfaces 310. Theincident mode notification may be received as a message or a set ofrelated messages that include instructions for the observercommunication device 300 to operate in the incident mode. In anembodiment, the incident mode may control the operation ofcommunications interfaces 310 and applications, may dictate the displayavailable at user interface 306, and may operate sensors 308 in order toprovide monitoring. Once the incident mode notification has beenreceived, processing may continue to step 704.

At step 704, processing element 302 of observer communication device 300may execute communication instructions 320 in order to control theoperations of communications interfaces 310. Based on the incident modenotification, some or all of communications interfaces such as cellular,Wi-Fi, Bluetooth, Near Field communications (“NFC”), Ethernet, USB,FireWire, and other communications interfaces, may be modified such thatthey are either disabled or limited such that only certaincommunications are permitted to be exchanged via the communicationsinterface (e.g., communications from the incident mode application). Forexample, in an embodiment, only communications from the incident modeapplication may be transmitted via communications interfaces 310 and allcommunications interfaces except for SMS, Wi-Fi, and Ethernet may bedisables. Once the operation of the communications interfaces 310 hasbeen modified, processing may continue to step 706.

At step 706, processing element 302 of observer communication device 300may execute user interface instructions 322 to update the operation ofuser interface 306 based on the incident mode notification. As describedherein, the user interface 306 may be modified such that some or allapplications other than the incident mode application are inaccessiblevia user interface 306. User interface 306 may also be modified todepict the incident mode application, which may provide information suchas information about the incident, information about assailants,instructions for observers, personalized instructions for observers in acertain area, and specific questions and interfaces to facilitateobservers providing information relating to the incident. Once the userinterface 306 has been updated, processing may continue to step 708.

At step 708, processing element 302 of observer communication device 300may execute monitoring instructions 326 to modify the operation ofsensors 308 based on the incident mode notification. In someembodiments, certain sensors (e.g., cameras and microphones) may beenabled in order to provide monitoring of the area where the observer islocated. In some embodiments, the monitoring may only be enabled when alocation (e.g., a GPS location) indicates that the observer is in anarea approximate to the incident, or in response to an input at the userinterface (e.g., the user interface 306 of the incident modeapplication). Once the monitoring performed by sensors 308 has beenupdated, processing may continue to step 710.

At step 710, processing element 302 of observer communication device 300may execute user interface instructions 322 and monitoring instructions326 to receive data from the user interface 306 and sensors 308. In someembodiments, some of the data received data may be processed at theobserver communication device 300 in order to determine whetherinformation should be provided to the monitoring system 300 and/or toprovide preliminary analysis of the received data. For example, in anembodiment, audio data may be analyzed to determine if a gunshot hasoccurred in the area. Once the data has been received from the userinterface 306 and sensors 308, processing may continue to step 612.

At step 712, processing element 302 of observer communication device 300may execute the communication instructions 320 in order to transmit thereceived and processed data to the monitoring station 30 viacommunications interfaces 310. Once the data has been transmitted,processing may continue to step 714.

At step 714, processing element 302 of observer communication device 300may execute communication instructions 320 to determine whether amessage indicating that the incident mode is over has been received viacommunications interfaces 310. As described herein, a message may beprovided that indicates that the incident mode is over, providinginstructions for exiting the incident or summary information about theincident, and allowing the observer communication device 300 to exit theincident mode. If such a message has been received, processing maycontinue to step 716. If such a message has not been received,processing may continue to step 718.

At step 716, processing element 302 may execute communicationinstructions 320, user interface instructions 322, and monitoringinstructions 326 to restore each of the user interface 306, sensors 308,and communications interfaces 310 to the normal mode. In someembodiments, information may also be provided to user interface 306providing instructions, information, and information requests related tothe end of the incident. In some embodiments, one or more messages maybe sent via communications interfaces 310 indicating that an incident isover (e.g., a text message transmitted to individuals on an “in case ofemergency” list). Once the incident mode has been exited, processing mayend.

At step 718, processing element 302 of observer communication device 300may execute communication instructions 320 to determine if an updatemessage has been received via communications interfaces 310. An updatemessage may provide changed parameters for any of user interface 306,sensors 308, and communications interfaces 310. If an update message hasnot been received, processing may return to step 710, in which data fromthe user interface 306 and sensors 308 may be received according to theexisting parameters of the incident mode. If an update message has beenreceived, processing may return to step 704, such that the operation ofthe user interface 306, sensors 308, and communications interfaces 310may be updated.

FIG. 8 depicts exemplary steps for operating a responder device inresponse to an incident in accordance with some embodiments of thepresent disclosure. The steps of FIG. 8 are provided in an exemplarysequence and flow, and it will be understood that some steps may beinserted or removed, and that a different flow and steps may beimplemented.

At step 802, processing element 502 of responder device 500 may executeinstructions of communication instructions 520 to receive communicationsfrom monitoring station 30 via communications interfaces 510. Thecommunications may be received as a message or a set of related messagesthat include information about an incident for use by the responderdevice 500. In an embodiment, the responder device 500 may utilizeinformation from the monitoring station 30 (and in some embodiments,from other responder devices 500) to control the display available atuser interface 506, to operate sensors 508 (e.g., to assist responderand to provide monitoring to monitoring station 30), and to control theoperation of communications interfaces 510. Once the incidentinformation has been received, processing may continue to step 804.

At step 804, processing element 502 of responder device 500 may executeuser interface instructions 522 to update the user interface 506 basedon communications from the monitoring station 30 and other responderdevices 500. As described herein, the user interface 506 may be modifiedto display information about an incident, to display informationrequests from the monitoring station 30 or other responder devices 50,to provide a rich descriptive display with information about an incidentintegrated into a map of the sub-region, and to enable other interfacesto control responder equipment and communicate with other responderdevices 500. In an embodiment, the user interface 506 may initiallydisplay information about the incident (e.g., type of incident,assailant information, number of observers, and injuries) and a requestthat the responder indicate whether he will respond to the incident. Ifthe responder answers yes, the responder device 500 may initiate thedescription display to provide information about the incident, andinclude other information such as links to engage in directcommunications with other responders who are responding directly to theincident. Once the user interface 506 has been updated, processing maycontinue to step 806.

At step 806, processing element 502 of responder device 500 may executemonitoring instructions 526 to operation the sensors 508 in response tothe incident. In some embodiments, certain sensors (e.g., cameras andmicrophones) may provide monitoring that may be transmitted to themonitoring station 30. In some embodiments, the monitoring may only beenabled when a location (e.g., a GPS location) indicates that theresponder is in an area approximate to the incident of if the responderindicates that the monitoring should be provided (e.g., via userinterface 506). Once the monitoring performed by sensors 508 has beenupdated, processing may continue to step 808.

At step 808, processing element 502 of responder device 500 may executecommunication instructions 520 in order to communicate with otherresponder devices 500. Responder devices 500 may communicate informationsuch voice, video, audio, location, and information regarding anincident via communication interfaces 510 such as cellular, radio, andsatellite communication interfaces. In this manner, responder devices500 for responders that are responding to an incident may communicateinformation about the incident in the background (e.g., withoutintervention from the responders) and responders may also communicatedirectly. Processing may then continue to step 810.

At step 810, processing element 502 of responder device 500 may executeuser interface instructions 522 and monitoring instructions 526 toreceive data from the user interface 506 and sensors 508. In someembodiments, some of the data received data may be processed at theresponder device 500 in order to determine whether information should beprovided to the monitoring system 500 and/or to provide preliminaryanalysis of the received data. For example, in an embodiment, audio datamay be analyzed to determine if a gunshot has occurred in the area. Oncethe data has been received from the user interface 506 and sensors 508,processing may continue to step 612.

At step 812, processing element 502 of responder device 500 may executethe communication instructions 520 in order to transmit the received andprocessed data to the monitoring station 30 via communicationsinterfaces 510. Once the data has been transmitted, processing maycontinue to step 814.

At step 814, processing element 502 of responder device 500 may executecommunication instructions 520 to determine whether a message indicatingthat the incident is over has been received via communicationsinterfaces 510. As described herein, a message may be provided thatindicates that the incident is over, providing instructions for exitingthe incident or summary information about the incident, and allowing theresponder device 500 to respond to other incidents. If such a messagehas been received, processing may continue to step 816. If such amessage has not been received, processing may continue to step 818.

At step 816, processing element 502 may execute communicationinstructions 520, user interface instructions 522, and monitoringinstructions 526 to restore each of the user interface 506, sensors 508,and communications interfaces 510 to a mode in which the responderdevice is no longer responding to the incident. In some embodiments,information may also be provided to user interface 506 providinginstructions, information, and information requests related to the endof the incident. In some embodiments, the responder devices 500 thatwere responding to the incident may cease communicating with each other,and background monitoring of sensors of responder devices may cease.Processing may end.

At step 818, processing element 502 of responder device 500 may executecommunication instructions 520 to determine if an update message hasbeen received via communications interfaces 510. An update message mayprovide changed parameters for any of user interface 506, sensors 508,and communications interfaces 510. If an update message has not beenreceived, processing may return to step 810, in which data from the userinterface 506 and sensors 508 may be received according to the existingparameters of the responder device 500. If an update message has beenreceived, processing may return to step 804, such that the operation ofthe user interface 506, sensors 508, and communications interfaces 510may be updated.

FIG. 9 depicts an exemplary monitored region in accordance with someembodiments of the present disclosure. FIG. 9 depicts a portion 902 of alarger monitored region 10 (e.g., a jurisdictional area for a lawenforcement entity). In an exemplary embodiment, portion 902 of themonitored region 10 may correspond to a display provided to an operatorat a monitoring station 30 for use by the operator in determining asub-region for which to invoke the incident mode. FIG. 9 depicts a gridoverlying the portion 902, the grid including numerical indicators 906corresponding to longitudinal gridlines and alphabetical indicators 904corresponding to latitudinal gridlines. In an exemplary embodiment, asdescribed herein, computing systems and/or the operator may determinethe sub-region from notifications based on the user interface providedto the operator.

FIG. 10 depicts an exemplary sub-region based on the portion 902depicted in FIG. 9. The portion 902 may have shading 1004 that indicateswhere the sub-region of the monitored region exists within portion 902.As depicted in FIG. 10, the sub-region of the monitored region may beindicated by shaded blocks 1004.

FIG. 11 depicts an exemplary user interface of an operator communicationdevice in accordance with some embodiments of the present disclosure. Inan embodiment, user interface may include a notification portion 1102,an instructions portion 1104, user interface portions 1106, 1108, and1110, and an emergency notification portion 1112. Although emergencynotification portion 1102 may include any suitable information asdescribed herein, in the embodiment of FIG. 11, emergency notificationportion 1102 may inform the observer that there is an active shooter inthe observer's area and provide the physical description of the activeshooter. Although instructions portion 1104 may include any suitableinstructions as described herein, in an embodiment, instructions portion1104 may provide instructions for responding to a request forinformation about the active shooter. Although user interface portions1106, 1108, and 1110 may provide any suitable information as providedherein, in an exemplary embodiment, user interface portion 1106 mayprovide an option that allows the observer to indicate that they havenot seen or heard gunshots. In an embodiment, user interface portion1108 may provide an input for the observer to indicate they have notseen a shooter but can hear gunshots. In an embodiment, user interfaceportion 1110 may allow an observer to indicate that they see the shooterand hear gunshots. Emergency notification portion 1112 may provide aninput that allows the observer to provide information regarding anemergency condition such as an injury. In some embodiments (not depictedin FIG. 11), providing an input to the emergency notification mayprovide a sub-menu including a set of options regarding the nature andseverity of an injury.

FIG. 12 depicts an exemplary user interface of a responder 40 inaccordance with some embodiments of the present disclosure. Although auser interface of a responder 40 may include any suitable user interfaceelements, in an embodiment in an initial user interface provided toalert a responder to the incident may include a descriptive portion1202, a user input portion 1204, and a descriptive map portion 1206. Inan embodiment, descriptive portion 1202 may provide a description of theincident, the location, and a description of any assailant. In anembodiment, user input portion 1204 may provide an indicator that allowsthe responder to say that they will respond to the incident. In anembodiment, descriptive map portion 1206 may include a map of thesub-region, as well as indicators relating to the possible location ofan assailant (e.g., an active shooter).

FIG. 13 depicts an exemplary descriptive map portion 1302 in accordancewith some embodiments of the present disclosure. Although a descriptivemap portion 1302 may include any suitable information as describedherein, in an embodiment, the descriptive map portion 1302 may includeinformation depicting the locations of responders 40 and informationrelating to observer responses regarding gunshots. In the embodiment ofFIG. 13, responders 40 are indicated by dots having a distinctive color,as indicated by 1304. Indicators 1306 may signify observer responsesregarding the locations of gunshots. Different colors and/or shadingsmay convey different information related to the observer's observations.For example, a green color may indicate that a gunshot was neither seennor heard, a yellow indicator may indicate that a gunshot was heard butthe shooter was not seen, and a red indicator may indicate that ashooter was seen and the gunshot was heard. Based on this information,the responders can quickly indicate the likely location of an activeshooter. In addition, shading may be used to indicate how recently aparticular response was received. For example, any of the greenindicator, yellow indicator, or red indicator may reduce in intensity astime elapses since the response was provided. In this manner, respondersmay be able to identify a movement path of an assailant.

It will be understood that aspects of the systems, apparatuses,structures, and methods describe herein may be modified to be furtheroptimized, and that the foregoing disclosure merely provides anillustration of the principles therein, that that those skilled in theart may make such modifications without departing from the scope of thisdisclosure. The embodiments described herein are not intended to belimiting, but are provided instead for purposes of illustration.Accordingly, the subject matter described herein should be understoodand construed with the full scope and breadth in accordance with thefollowing claims.

What is claimed is:
 1. A method for monitoring and responding to anincident, comprising: sending a monitoring message from a mobile deviceto a monitoring station, wherein the monitoring message includesmonitored data about the incident and location information relating to alocation of the incident, wherein the monitoring station generates anincident message including incident information based on the monitoreddata and the location information; receiving, at the mobile device, theincident message; disabling access of one or applications of the mobiledevice to one or more communication interfaces of the mobile devicebased on the incident message; disabling access of the one orapplications to a user interface of the mobile device based on theincident message; providing, at the user interface, an incident modeuser interface based on the incident information; receiving, via theuser interface, descriptive information about the incident based on theincident mode user interface; generating, at the mobile device, aresponse message that includes the descriptive information; transmittingthe response message from the mobile device to the monitoring station,wherein the monitoring station generates an update message based on thedescriptive information, and wherein the update message includes updatedincident information; receiving, at the mobile device, the responsemessage; and updating the incident mode user interface based on theresponse message.
 2. The method of claim 1, further comprising:disabling access of the one or more applications to at least one sensorof the mobile device; and collecting sensor data from the at least onesensor, wherein the response message includes the collected sensor data.3. The method of claim 2, wherein the at least one sensor comprises acamera or a microphone.
 4. The method of claim 1, further comprising:collecting sensor data from at least one sensor of the mobile device;and identifying, at the mobile device, a gunshot based on the collectedsensor data, wherein the response message includes an indication of theidentified gunshot.
 5. The method of claim 1, wherein the incident modeuser interface comprises a notification portion and a user interfaceportion.
 6. The method of claim 5, wherein the notification portiondepicts a location of the incident within a map region.
 7. The method ofclaim 6, wherein the notification portion depicts a location of one ormore responders within the map region.
 8. The method of claim 1, furthercomprising disabling at least one of the one or more communicationinterfaces in response to the incident message.
 9. The method of claim1, wherein the monitoring station receives a plurality of additionalmonitoring messages from a plurality of additional mobile devices,wherein each monitoring message includes monitored data about theincident and location information relating to a location of theincident, and wherein the monitoring station generates the incidentmessage having incident based on the plurality of monitoring messages.10. The method of claim 9, wherein the monitoring state generates theupdate message based on a plurality of additional response messages froma plurality of additional mobile devices, and wherein each of theplurality of additional response messages includes additionaldescriptive information.
 11. A mobile device, comprising a communicationinterface; a user interface; a processing element coupled to the one ormore communication interface and the user interface; and memory coupledto the processing element and having instructions stored thereon thatwhen executed by the processing element cause the processing element to:generate a monitoring message, wherein the monitoring message includesmonitored data about an incident and location information relating to alocation of the incident; transmit, via the communication interface, themonitoring message to a monitoring station, wherein the monitoringstation generates an incident message including incident informationbased on the monitored data and the location information; receive, viathe communication interface, the incident message; disable access of oneor applications of the mobile device to the communication interfacebased on the incident message; disable access of the one or applicationsto the user interface based on the incident message; provide, at theuser interface, an incident mode user interface based on the incidentinformation; receive, from the user interface, descriptive informationabout the incident based on the incident mode user interface; generate aresponse message that includes the descriptive information; transmit theresponse message to the monitoring station via the communicationinterface, wherein the monitoring station generates an update messagebased on the descriptive information, and wherein the update messageincludes updated incident information; receive, via the communicationinterface, the response message; and update the incident mode userinterface based on the response message.
 12. The mobile device of claim11, further comprising at least one sensor, wherein the instructionsfurther cause the processing element to: disable access of the one ormore applications to the at least one sensor; and collect sensor datafrom the at least one sensor, wherein the response message includes thecollected sensor data.
 13. The mobile device of claim 12, wherein the atleast one sensor comprises a camera or a microphone.
 14. The mobiledevice of claim 11, further comprising at least one sensor, wherein theinstructions further cause the processing element to: collect sensordata from the at least one sensor; and identify a gunshot based on thecollected sensor data, wherein the response message includes anindication of the identified gunshot.
 15. The mobile device of claim 11,wherein the incident mode user interface comprises a notificationportion and a user interface portion.
 16. The mobile device of claim 15,wherein the notification portion depicts a location of the incidentwithin a map region.
 17. The mobile device of claim 16, wherein thenotification portion depicts a location of one or more responders withinthe map region.
 18. The mobile device of claim 11, further comprising asecond communication interface, wherein the instructions further causethe processing element to disable the second communication interface inresponse to the incident message.
 19. The mobile device of claim 11,wherein the monitoring station receives a plurality of additionalmonitoring messages from a plurality of additional mobile devices,wherein each monitoring message includes monitored data about theincident and location information relating to a location of theincident, and wherein the monitoring station generates the incidentmessage having incident based on the plurality of monitoring messages.20. The mobile device of claim 19, wherein the monitoring stategenerates the update message based on a plurality of additional responsemessages from a plurality of additional mobile devices, and wherein eachof the plurality of additional response messages includes additionaldescriptive information.
 21. A non-transitory computer-readable storagemedium of a mobile device comprising instructions stored therein, whichwhen executed by one or more processors of the mobile device, cause theone or more processors to perform operations comprising: sending amonitoring message to a monitoring station, wherein the monitoringmessage includes monitored data about the incident and locationinformation relating to a location of the incident, wherein themonitoring station generates an incident message including incidentinformation based on the monitored data and the location information;receiving the incident message; disabling access of one or applicationsof the mobile device to one or more communication interfaces of themobile device based on the incident message; disabling access of the oneor applications to a user interface of the mobile device based on theincident message; providing, for display the user interface, an incidentmode user interface based on the incident information; receiving, viathe user interface, descriptive information about the incident based onthe incident mode user interface; generating a response message thatincludes the descriptive information; transmitting the response messageto the monitoring station, wherein the monitoring station generates anupdate message based on the descriptive information, and wherein theupdate message includes updated incident information; receiving theresponse message; and updating the incident mode user interface based onthe response message.